feat(views): add ephemeral PQC worklist contract - #125

• OWNERS [chubirka]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

• Define a packaged PQC worklist schema with explicit scope and preserved legacy entry data.
• Distinguish unknown states from measured values without restricting raw historical strings.
• Test accepted and rejected documents and document Core’s ownership of worklist behavior.

graph TD
  Core["Core worklist"] --> View["Ephemeral wrapper"] --> Entries["Worklist entries"] --> Access["Liveness data"]
  Entries --> Scan["Scan state"]
  Schema["PQC schema"] --> View
  View --> Consumer["Core consumers"]

Loading

Keep this as a data-only view schema, consistent with the existing ephemeral view contract. Putting worklist behavior in contracts or modeling the view as a persisted artifact would blur Core ownership and add storage semantics this change does not need.

Enhancement (1) +92 / -0

pqc-worklist.schema.jsonDefine the ephemeral PQC worklist JSON Schema +92/-0

Define the ephemeral PQC worklist JSON Schema

• Adds a strict Draft 2020-12 wrapper with explicit product and ref scope, chokepoints, and entries containing nested liveness and nullable scan state. Requires serialized fields while retaining nullable observations and unconstrained historical strings.

views_schema/v1/pqc-worklist.schema.json

Tests (1) +239 / -0

test_pqc_worklist_view.pyExercise PQC worklist schema acceptance and rejection +239/-0

Exercise PQC worklist schema acceptance and rejection

• Adds validation cases for required and unknown fields, scope and nullable states, existing tiers and routes, and unrestricted raw strings. Rejects invalid identifiers, timestamps, types, and vocabulary values.

tests/test_pqc_worklist_view.py

Documentation (1) +24 / -0

README.mdDocument PQC worklist semantics and Core ownership +24/-0

Document PQC worklist semantics and Core ownership

• Explains scope selection, required nested data, nullable observations, and the treatment of raw strings. Clarifies that Core owns production and rendering, while the view is neither persisted nor a replacement for the legacy CLI output.

README.md

💡 Did you know, you can switch off images and animations for a plain-text comment

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗